Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respect load strictness when calling load_state_dict #10665

Closed
wants to merge 6 commits into from

Conversation

mikolajblaz
Copy link
Collaborator

What does this PR do ?

model.dist_ckpt_load_strictness allows to ignore mismatches during checkpoint loading.
Still, loading a state dict can yield errors. This PR ensures this flag is respected also during load_state_dict.

Collection: [Note which collection this PR will affect]

Changelog

  • Add specific line by line info of high level changes in this PR.

Usage

  • You can potentially add a usage example below
# Add a code snippet demonstrating how to use this 

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests?
  • Did you add or update any necessary documentation?
  • Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
    • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

  • New Feature
  • Bugfix
  • Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

  • Related to # (issue)

@github-actions github-actions bot added core Changes to NeMo Core NLP labels Sep 27, 2024
Signed-off-by: mikolajblaz <mikolajblaz@users.noreply.github.com>
Copy link
Contributor

This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or update or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Oct 17, 2024
@mikolajblaz mikolajblaz marked this pull request as ready for review October 21, 2024 09:49
@mikolajblaz
Copy link
Collaborator Author

According to @ashors1 this type of change is not needed for NeMo 2.0, so should be ready to go, @dimapihtar can you review?

@ashors1
Copy link
Collaborator

ashors1 commented Oct 21, 2024

According to @ashors1 this type of change is not needed for NeMo 2.0, so should be ready to go, @dimapihtar can you review?

I think there was a miscommunication here. This change is needed for NeMo 2.0, but I think we can handle that in a separate PR.

@github-actions github-actions bot removed the stale label Oct 22, 2024
Copy link
Contributor

github-actions bot commented Nov 6, 2024

This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or update or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Nov 6, 2024
Copy link
Contributor

This PR was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Changes to NeMo Core NLP stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants